The Web API Design Guidelines for Happy Developers: A short pragmatic guide to build effective and funny Web APIs by

The Web API Design Guidelines for Happy Developers: A short pragmatic guide to build effective and funny Web APIs by

Language: eng
Format: azw3
Published: 2015-12-22T16:00:00+00:00


Repeatedly exceeding the allocated limits, can cause the offending user account to be black-listed and/or notified of the problem. Depending on the use case, you might even want to charge the user for the extra costs incurred.

Actions

The good, old HTTP methods are enough to model our web APIs following a CRUD paradigm, but… what about expressing other actions on resources? For example, think for a moment about a resource that can be activated or deactivated (start, stop or on, off). Yes, sure, you may argue that a resource can have a status, which can be updated with a PUT, like calling:

PUT /v1/things/2 HTTP/1.1 Host: https://api.example.org Content-Type: application/json { "status": "ON", {...} }



Download



Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.